home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20031118-20041115
/
000215_fdc@columbia.edu_Thu Apr 15 11:28:40 2004.msg
< prev
next >
Wrap
Internet Message Format
|
2004-11-14
|
2KB
Path: newsmaster.cc.columbia.edu!not-for-mail
From: Frank da Cruz <fdc@columbia.edu>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit-C and logging
Date: 15 Apr 2004 15:27:04 GMT
Organization: Columbia University
Lines: 32
Message-ID: <slrnc7tae8.4fi.fdc@sesame.cc.columbia.edu>
References: <oRwfc.343$kb.20640@news.uswest.net>
Reply-To: fdc@columbia.edu
NNTP-Posting-Host: sesame.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1082042824 6735 128.59.59.56 (15 Apr 2004 15:27:04 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 15 Apr 2004 15:27:04 GMT
User-Agent: slrn/0.9.8.0 (SunOS)
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14929
On 2004-04-15, root <root@sbic.com> wrote:
: I'm trying to log the call records for our VoIP system using Kermit. It
: works fine individually, but I have 5 seperate boxes that I telnet into on
: port 1752, the data streams through and I have Kermit grab it and file it
: into a log.
:
: It's a LOT cheaper than any call logging program out there and it works
: great. The problem I have however is that I can't get my linux box to
: automatically run these 5 seperate kermit sessions on boot. I'm using Red
: Hat Enterprise and I also want to be able to monitor these sessions with
: Big Brother.
:
What's the problem? You can start up one process on boot, but not five?
Or you can't start up any processes on boot?
In the latter case, there is always the possibility that Kermit is
trying to print some message to standard output, when there is no standard
output (this should not happen, but it's possible). In that case, part
of your Kermit invocation should be to redirect standard output to a file
or to /dev/null.
Do you want all five processes to log to the same file? Kermit is not
designed for that, but it can still be done with some creative script
programming. Basically, you need your script to not just blindly log
the incoming stream to a file, but to parse it looking for records
(lines or whatever), and then when it gets one, open the log file for
exclusive append access (and if fail, keep trying until it succeeds),
write out the record, close the file. You might also want to put
timestamps and session signatures on each record, in case they don't
already have these.
- Frank